Automatic meta-data sharing of existing media to create streamable collections

ABSTRACT

A method, system, and/or apparatus of automatic meta-data sharing of existing media to create streamable collections are disclosed. In one embodiment, a method of a server device includes analyzing a media data of a client device to determine at least one meta-data identifier associated with the media data and automatically populating a new mark-up language file using a existing media-collection data associated with certain items of the media data, and creating a streamable media content of the existing media-collection data on the server device based on a reference of the at least one meta-data identifier associated with each of the existing media collection data with a content database of a central server. The method may include communicating the streamable media content from the central server to the user on any client device without requiring consideration of the user to access the media content.

CLAIMS OF PRIORITY

This patent application claims priority from:

(1) U.S. Utility patent application Ser. No. 11/375,911 filed on Mar.15, 2006.

FIELD OF TECHNOLOGY

This disclosure relates generally to the technical fields of software,database, and/or hardware technology and, in one example embodiment, toa method, system, and/or apparatus of automatic meta-data sharing ofexisting media to create streamable collections.

BACKGROUND

A user (e.g., a music fan, a movie patron, a computer gaming patron, ane-book reader) may purchase a media content (e.g., musical, theatrical,artistic, cultural, hobby, etc.) through a service (e.g., Apple® iTunes,Napster®, Rhapsody®, etc.). The user may download the media content to aclient device (e.g., a home computer, a work computer, a laptop, aportable media player, etc.) after purchase from the service. The usermay have multiple client devices from which the user may wish to access(e.g., listen to) the media content.

Sometimes, the user may wish to access the media content from clientdevices of others (e.g., friends, strangers, from a web café, etc.). Theuser may copy the media content after downloading it to the clientdevice. However, this may violate a copyright protection (e.g.,duplication license, distribution license, reproduction limitation) ofan owner of the media content. Furthermore, the media content may failto operate from client devices not authorized by the owner of the mediacontent. As a result, the user may not have universal access to themedia content from any client device.

SUMMARY

A method, system, and/or apparatus of automatic meta-data sharing ofexisting media to create streamable collections are disclosed. In oneaspect, a method of a server device includes analyzing a media data of aclient device to determine at least one meta-data identifier associatedwith the media data, automatically populating a new mark-up languagefile using a existing media-collection data associated with certainitems of the media data, and creating a streamable media content of theexisting media-collection data on the server device based on a referenceof the at least one meta-data identifier associated with each of theexisting media collection data with a content database of a centralserver.

The method may include communicating the streamable media content fromthe central server to the user on any client device without requiringconsideration of the user to access the media content. The contentdatabase may include content of artists and/or media labels.

The meta-data identifier may be generated by a client application thatis agnostic of a type of media player application compatible with themedia data. The new mark-up language file may include an arrangement(e.g., a collection, a hierarchy, etc.) of the existing media-collectiondata of the certain items associated with the media data of the clientdevice. The existing media-collection data may be executable byinterested parties as a radio station.

The new mark-up language file and the arrangement may be associated witha particular user. In addition, the particular user may be associatedwith other mark-up language files associated with other users based onsimilar attributes in the arrangement of the particular user and otherarrangements associated with the other users. A compatibility rating maybe determined between the user and the other users based on the similarattributes between the arrangement and the other arrangements and eachuser of the server device may be enabled to view mark-up language filesof the other users. A particular one of the other users may beregistered when the particular one of the other users responds to a hookdata in a communication between the user and the other users. A groupmay be formed between the user and at least one of the other users basedon a threshold parameter of the compatibility rating. The other usersmay include an admired user whose contribution is shared with the group.

The new mark-up language file may include a 30 second media segment ofcertain items of the media data that is associated with the existingmedia-collection. The media data may be a multimedia data and themeta-data identifier may be determined primarily based on an audio dataembedded in the multimedia data. The existing media-collection data maybe generated by analyzing a usage pattern of at least one of the clientdevice and a peripheral device. The peripheral device may be a portablemedia player and the client device may be a two-way mobile communicationdevice.

A widget chosen from a group including a party widget, a personaldetails widget, a tag widget, a guestbook widget, an internal messagingwidget, a share widget, a photo widget, a tuned-in now widget, a postwidget, a reviews widget, and/or a live event widget may be applied tothe new mark-up language file. The widget may be a drag and drop widgetand the content data created using the post widget may be automaticallydisplayed on the new mark-up language file and an artist mark-uplanguage file, an album mark-up language file, a particular item mark-uplanguage file, and/or a fan club mark-up language file. The content datamay be displayed before other content data when a peer client deviceaffiliated with the client device reaches the artist mark-up languagefile, the album mark-up language file, the particular item mark-uplanguage file, and/or the fan club mark-up language file through the newmark-up language file.

A payment may be processed from an interested party when the new mark-uplanguage file develops a patron base above a threshold value and anadvertisement of the interested party may be displayed on the newmark-up language file. The new mark-up language file may be localized inany number of languages including English, Japanese, Korean, Hindi,German, French, Russian, Arabic, Hebrew, Spanish, Mandarin, Cantoneseand/or Italian.

In another aspect, a method of a client device includes communicating amedia data to a server device to determine at least one meta-dataidentifier associated with the media data and automatically refreshing anew mark-up language file using a existing media-collection dataassociated with the certain items of the media data. The new mark-uplanguage file includes a streamable version of the media data based onthe meta-data identifier being referenced with a content database of acentral server.

The media data may not be transferred from the client device to thecentral server. The streamable version of the media data may beaccessable across different client devices associated with a user. Themethod may include applying the meta-data identifier may be applied(e.g., such that it may be agnostic of a type of media playerapplication compatible with the media data). The method may includedeveloping an arrangement of the existing media-collection dataassociated with the certain items of the media data.

In yet another aspect, a network includes a client device to apply atleast one meta-data identifier such that it is agnostic of a type ofmedia player application compatible with the media data and a serverdevice to automatically populate a new mark-up language file using aexisting media-collection data associated with at least some contentidentified by the at least one meta-data identifier and to create astreamable media content of the existing media-collection data on theserver device based on a reference of the at least one meta-dataidentifier associated with each of the existing media collection datawith a content database of a central server.

In addition the network may include a peer client device that may beassigned a kin status with the client device based on similarity betweenthe existing media-collection data of the client device and anotherexisting media-collection data of the peer client device. The networkmay also include an admired client device to share an admiredmedia-collection data with the client device and the peer client device.

The methods, systems, and apparatuses disclosed herein may beimplemented in any means for achieving various aspects, and may beexecuted in a form of a machine-readable medium embodying a set ofinstructions that, when executed by a machine, cause the machine toperform any of the operations disclosed herein. Other features will beapparent from the accompanying drawings and from the detaileddescription that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

Example embodiments are illustrated by way of example and not limitationin the figures of the accompanying drawings, in which like referencesindicate similar elements and in which:

FIG. 1 is a network view of a server device, a client device, a peerclient device and an admired client device communicating media datathrough a network, according to one embodiment.

FIG. 2 is block diagram of the server device of FIG. 1, having a mediarequestor module, a media processing module, a profile generator module,a transaction module, and a user group generator module, according toone embodiment.

FIG. 3 is an exploded view of the profile generator module of FIG. 2,according to one embodiment.

FIG. 4 is an exploded view of the client application module of FIG. 1,according to one embodiment.

FIG. 5 is a system view of the client application module of FIG. 1communicating media data from a peripheral device and/or a client deviceto a new mark-up language file through a network.

FIG. 6 is a diagrammatic representation of a data processing systemcapable of processing a set of instructions to perform any one or moreof the methodologies herein, according to one embodiment.

FIG. 7 is a user interface view of the widget select module of FIG. 3,according to one embodiment.

FIG. 8 is a user interface view of the new mark-up language file of FIG.2, according to one embodiment.

FIG. 9 is a user interface view of the artist mark-up language file,according to one embodiment.

FIG. 10 is a user interface view of the override module of FIG. 2,according to one embodiment.

FIG. 11A is a flow chart illustrating a method to automatically populatea new mark-up language file using an existing media-collection dataassociated with certain items of the media data, according to oneembodiment.

FIG. 11B is a flow chart that describes further the operations in FIG.11A, according to one embodiment.

FIG. 12 is a flow chart illustrating a method of the client device tocommunicate media data to the server device and refreshing a new mark-uplanguage file, according to one embodiment.

Other features of the present embodiments will be apparent from theaccompanying drawings and from the detailed description that follows.

DETAILED DESCRIPTION

A methods, systems and/or apparatus of automatic meta-data sharing ofexisting media to create streamable collections are disclosed. In thefollowing description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the various embodiments. It will be evident, however tothe one skilled in the art that the various embodiments may be practicedwithout these specific details.

In one embodiment, a methods of a server device 100 (as illustrated inFIG. 1) includes analyzing a media data 116 (e.g., the media data 116 ofFIG. 1) of a client device 104 (as illustrated in FIG. 1) to determineat least one meta-data identifier associated with the media data 116,automatically populate a new mark-up language file (e.g., the newmark-up language file 214 of FIG. 2) using a existing media-collection(e.g., an history of media consumed by a user) data associated withcertain items of the media data 116, and creating a streamable mediacontent (e.g., audio, video, etc.) of the existing media-collection dataon the server device 100 based on a reference of the at least onemeta-data identifier associated with each of the existing mediacollection data with a content database of a central server (e.g., thecentral server 118 of FIG. 1).

In another embodiment a method of a client device 104 includescommunicate a media data 116 to a server device 100 to determine atleast one meta-data identifier associated with the media data 116 and toautomatically refresh a new mark-up language (e.g., the new mark-uplanguage file 214 of FIG. 2) using a existing media-collection dataassociated with certain items of the media data 116. The new mark-uplanguage file 214 includes a streamable version of the media data basedon the meta-data identifier being referenced with a content database ofa central server (e.g., the central server 118 of FIG. 1).

In yet another embodiment a network 102 includes a client device 104 toapply at least one meta-data identifier such that it is agnostic of atype of media player application compatible with the media data 116 anda server device 100 to automatically populate a new mark-up languagefile (e.g., the new mark-up language file 214 of FIG. 2) using aexisting media-collection data associated with at least some contentidentified by the at least one meta-data identifier and to create astreamable media content of the existing media-collection data on theserver device based on a reference of the at least one meta-dataidentifier associated with each of the existing media collection datawith a content database of a central server (e.g., the central server118 of FIG. 1).

It will be appreciated that the various embodiments discussed hereinmay/may not be the same embodiment, and may be grouped into variousother embodiments not explicitly disclosed herein.

FIG. 1 is a network diagram of a server device 100, a client device 104,a peer client device 106, the central server 118, and an admired clientdevice 108 communicating a media data 116 through a network 102 (e.g.,an Internet network, a local area network, a wide area network, etc.)according to one embodiment. In one embodiment the client device 104 mayapply at least one meta-data identifier such that it is agnostic of atype of media player application (e.g., unknown of the type of mediaplayer application) compatible with the media data 116. The clientdevice 104 may include a client application module 110 and a peripheraldevice 112 according to one embodiment. The client application module110 may be best understood with reference to FIG. 4, as will later bedescribed. The central server 118 may be a set of computers that maystore applications and/or data files shared by many different people onthe network 102 (e.g., over an internet, etc.).

In one embodiment the server device 100 automatically populates a newmark-up language file (e.g., the new mark-up language file 214 of FIG.2) using a existing media-collection data associated with at least somecontent (e.g., media content) identified by the at least one meta-dataidentifier. The server device may create a streamable media content ofthe existing media-collection data on the server device based on areference of the at least one meta-data identifier associated with eachof the existing media collection data with a content database of thecentral server 118.

The peer client device 106 may be assigned a kin status with the clientdevice 104 (e.g., related to the client device 104) based on similaritybetween the existing media-collection data of the client device 104 andanother media-collection data (e.g., existing and/or new) of the peerclient device 106 according to one embodiment. In one embodiment theadmired client device 108 may share an admired media-collection data(e.g., a history data admired by the client device 104 and/or the peerclient device 106) with the client device 104 and the peer client device106. The client device 104, the peer client device 106 and the admiredclient device 108 may together form a client group 114 (e.g., shown onthe new mark-up language file 214 by the client group display 808 ofFIG. 8) based on similarities in the existing media-collection data.Additional details of FIG. 1 are best understood with reference to FIG.2, FIG. 3 and FIG. 4.

FIG. 2 is block diagram of the server device 100 of FIG. 1 having amedia requestor module 200, a media processing module 202, a profilegenerator module 204, a user profile database 206, a media database 208,a relationship module 210, an override module 212, a transaction module216, and a new mark-up language file 214 according to one embodiment.The media requestor module 200 may create a media data request (e.g.,request for media data 116 of FIG. 1) and the server device 100 maycommunicate the media data request to the client device 104 through thenetwork 102 as illustrated in FIG. 1, according to one embodiment.

In one embodiment the server device 100 may analyze the media data 116of the client device 104 to determine at least one meta-data identifierassociated with the media data 116 and may automatically populate a newmark-up language file (e.g., the new mark-up language file 214 of FIG.2) using a play-list history data (e.g., an existing media-collectiondata) associated with certain items of the media data 116. The serverdevice 100 communicating the streamable media content from the centralserver 118 to the user on any client device without requiringconsideration of the user to access the media content, wherein thecontent database includes content of a plurality of artists and medialabels.

Specifically the media processing module 202 may process the media data116 received from the client device 104. The media processing module 202may include a data analyzer 218 and media algorithms 220. The dataanalyzer 218 may be used to analyze the media data 116 using a processor(e.g., such as a processor 602 of FIG. 6) to determine at least onemeta-data identifier associated with the media data. The data analyzer218 may also reference the media algorithms 220 and/or a media database208 to analyze and/or process the media data 116 communicated by theclient device 104. The media data 116 received by the data analyzer 218may be multimedia data according to one embodiment. Particularly, the atleast one meta-data identifier may be determined by the data analyzer218 by referencing media algorithms 220 and/or media database 208 andcarrying out comparative analysis of the media data (e.g., comparison ofaudio data embedded in the multimedia data with a known value in themedia database 208) to identify content (e.g., media content) associatedto the at least one meta-data identifier.

The profile generator module 204 may be used to generate a user profile(e.g., a user media profile) based on analyzing a user's media data(e.g., analysis of a play-list history data associated with certainitems of the media data, meta-data identifier, etc.) communicated by theclient device 104 (as illustrated in FIG. 1) and associating anarrangement (e.g., any hierarchy, arrangement and/or collection such asa music collection on a hard drive) of the play-list history data (e.g.,e.g., existing media-collection data) and a new mark-up language file(e.g., the new mark-up language file 214 of FIG. 2) which may includethe arrangement of the play-list history data to the user. The profilegenerator module 204 is best understood with reference to FIG. 3, aswill later be described.

The relationship module 210 may establish relationships between aparticular user profile and other user profiles by associating aparticular user with other mark-up language files associated with otherusers based on similar attributes (e.g., songs, artists, albums, movies,genre, authors, etc.) in the arrangement (e.g., hierarchy of theplay-list history data) of the particular user and other arrangementsassociated with other users, according to one embodiment. In oneembodiment the relationship module 210 may include a profile analyzer222 and compatibility algorithms 224. The profile analyzer 222 mayreference the user profile database 206 and/or the compatibilityalgorithms 224 to analyze and establish relationships between aparticular user profile and other user profiles. Specifically, theprofile analyzer 222 may determine a compatibility rating between theuser and the other users based on similar attributes (e.g., songs,artists, albums, movies, genre, authors, etc.) between the arrangement(e.g., hierarchy of the play-list history data of the user) and theother arrangements (e.g., hierarchy of the play-list history data of theother user) and enable each user of the server device 100 (illustratedin FIG. 1) to view mark-up language files (e.g., web pages) of the otherusers.

In one embodiment the relationship module 210 may register (e.g., relateand/or connect) a particular one of the other users when the particularone of the other users responds to a hook data (e.g., an invitation toconnect, invitation to join a group, etc.) in a communication betweenthe user and the other users. The relationship module 210 may also forma group (e.g., the client group 114 illustrated in FIG. 1) between theuser (e.g., the client device 104 of FIG. 1) and at least one of theother users (e.g., the peer client device 106 of FIG. 1) based on athreshold parameter (e.g., a certain value) of the compatibility rating.

The group (e.g., the client group 114 illustrated in FIG. 1) may alsoinclude an admired user (e.g., the admired client device 108 of FIG. 1)whose contribution (e.g., play-list history data of the admired user,suggestions, media discovery, etc.) may be shared with the group. Therelationship module may automatically populate details of a group (e.g.,client group display 808 as illustrated in FIG. 8) to the user's mark-uplanguage file (e.g., the new mark-up language file 214 of FIG. 2). Theoverride module 212 may be used to facilitate a user override (e.g.,manually override automatic system settings) to modify the arrangementof the play-list history data associated with the media data 116.

In one embodiment the server device 100 of FIG. 1 may generate amodified arrangement based on applying an addition (e.g., adding mediacontent), deletion (e.g., deleting media content) and/or an adjust(e.g., changing and/or replacing media content) operation of the useroverride on the arrangement (e.g., hierarchy) and automaticallypopulating a new mark-up language file (e.g., the new mark-up languagefile 214 of FIG. 2) based on the modified arrangement. Specifically thearrangement of the play-list history data associated with media data 116communicated by the profile generator module 204 may be modified withthe help of a user interface (e.g., the user interface view of theoverride module 212 of FIG. 10) to generate a modified arrangement.

This modified arrangement may then be populated on the new mark-uplanguage file 214. For example, based on a particular user's usagepattern the system may decide a user's media history (e.g., “Summer of69” as the last song played, etc.) or a user's media rating (e.g., BryanAdams as the top artist this month, etc.). But the user may haveconsumed other media (e.g., listened to Aerosmith on a friend's computerand/or a radio station, etc.) which may not have been addressed by thesystem. User override may allow the user to manually override the systemsettings and replace media content with more accurate description of theuser's media consumption (e.g., replace Bryan Adams in the earlierexample with Aerosmith). The user interface view of override module 212is best understood with reference to FIG. 10, as will later bedescribed.

The profile generator module 204 may then be used to generate a new userprofile (e.g., modified user profile) based on the modified arrangement.The relationship module 210 may also be used to develop new groups(e.g., like the client group display 808 of FIG. 8) and relationshipsbased on the modified arrangement generated by the override module 212between the user (e.g., client device 104 of FIG. 1) and at least one ofthe other users (e.g., peer client device 106 and/or admired clientdevice 108) based on a threshold parameter of the new compatibilityrating. Specifically a new profile (e.g., modified user profile) for auser may be generated by associating the particular user with the newmark-up language file 214 and the modified arrangement. The particularuser may also be associated with other mark-up language files associatedwith other users based on similar attributes (e.g., songs, artists,albums, movies, genre, authors, etc.) in the modified arrangement (e.g.,hierarchy) of the particular user and other arrangements (e.g.,hierarchies) associated with other users. A new compatibility rating maybe determined between the user and the other users based on similarattributes between the modified arrangement and the other arrangementsby a procedure similar to the one described for the relationship module210 of FIG. 2.

In one embodiment, the modifying operation may be performed on a widgetfrom a group comprising of a party widget, a personal detail widget(e.g., the personal detail widget 816 of FIG. 8), a tag widget (e.g.,the tag widget 906 of FIG. 9), a guestbook widget, an internal messagingwidget (e.g., the internal messaging widget 904 of FIG. 9), a sharewidget (e.g., the share widget 814 of FIG. 8), a photo widget (e.g., thephoto widget 812 of FIG. 8), a tuned-in now widget (e.g., the tuned-innow widget 908 of FIG. 9), a post widget (e.g., the post widget 902 ofFIG. 9), a reviews widget, and/or a live event widget. Especially when adelete operation is performed on the post widget (illustrated in FIG.9), content data created using the post widget 902 may be automaticallydeleted from the new mark-up language file 214 and from an artistmark-up language file, an album mark-up language file, a particular itemmark-up language file, and/or a fan club mark-up language filesimultaneously. For example by deleting a particular post widget (e.g.,post on Bob Dylan) from the new mark-up language file (e.g., the newmark-up language file 214 of FIG. 2) the post not only gets deleted fromthe new mark-up language file 214 but also gets deleted from the artistmark-up language file (e.g., the artist mark-up language file 900 ofFIG. 9 belonging to Bob Dylan) simultaneously.

The transaction module 216 may process a payment from an interestedparty (e.g., vendor, service provider, etc.) when the new mark-uplanguage file (e.g., the new mark-up language file 214 illustrated inFIG. 2) develops a patron base (e.g., a fan following, popularity, etc.)above a threshold value (e.g., number of hits that the new mark-uplanguage file may receive) and may display an advertisement (e.g., theadvertisement 810 in FIG. 8) of the interested party on the new mark-uplanguage file 214.

In one embodiment, operations may begin in the server device 100 of FIG.1 when the media data 116 requested by the media requester module 200from the client device 104 is received by the media processing module202. Specifically, the media data 116 may be transmitted to the dataanalyzer 218. The data analyzer 218 may then reference media algorithms220 and/or media database 208 to determine the meta-data identifierand/or identify the content associated with the meta-data identifier ofthe media data 116 based on comparison of the audio data embedded in themultimedia data of media data 116 with the media database 208. Theprofile generator module 204 may then generate a user profile based onassociating the arrangement of the play-list history data of the mediadata and the new mark-up language file with the user. The user profilemay be stored in the user profile database 206. The profile generatormodule 204 may further process the media data and automatically populateit on the new mark up language file (e.g., based on the widgets selectedby the user though the widget select module 310 as described later inFIG. 3).

FIG. 3 is an exploded view of the profile generator module 204 of FIG. 2having a widget generator module 300, a data analyzer 302, a mediaupdate module 304, a media history module 306 and a media rating module308 according to one embodiment. The widget generator module 300 may beused to generate and apply widgets chosen (e.g., based on a preferenceof a user) from a group of widgets (e.g., a party widget, a personaldetails widget, a guestbook widget, an internal messaging widget, ashare widget, a photo widget, a tuned-in now widget, a post widget, areviews widget, a live event widget, and/or a media sample widget, etc.)to the new mark-up language file (e.g., the new mark-up language file214 of FIG. 2).

According to one embodiment the widget generator module 300 may includea widget select module 310, a tag module 312, a party module 314, aguestbook module 316, a tuned-in now module 318, a live event module320, a photo module 322, a reviews module 324, a personal detail module326, an internal messaging module 328, a post module 330, a share module332 and/or a media sample module 334. The widget select module 310 mayprovide a user interface for selecting widgets. The widget select module310 is best understood with reference to FIG. 7, as will later bedescribed.

The tag module 312 may be used to generate a tag widget (e.g., the tagwidget 906 of FIG. 9) to allow a user to avail the tag feature (e.g.,display top tags, tag a song, etc.) in the new mark-up language file 214(illustrated in FIG. 2). The party module 314 may be used to generate aparty widget to allow a user to publicize party information (e.g.,parties hosted next week, top parties, etc.) through the new mark-uplanguage file 214. The guestbook module 315 may be used to generate aguestbook widget to allow a user to receive comments (e.g., related tothe users page, suggestions, etc.) from other users through the newmark-up language file 214.

The tuned-in now module 318 may be used to generate a tuned-in nowwidget (e.g., the tuned-in now widget 908 of FIG. 9) which may bedisplayed on a artist mark-up language file (e.g., the artist mark-uplanguage file 900 of FIG. 9), an album mark-up language file, aparticular item mark-up language file and/or a fan club mark-up languagefile to provide a user with information about other users availingsimilar media content (e.g., other users tuned in to the same song,album, artist, etc.) in real time. The live event module 320 may be usedto generate a live event widget to allow a user to provide informationregarding live events (e.g., live events happening this week, best liveevents in the country, etc.) on the new mark-up language file 214. Thephoto module 322 may be used to generate a photo widget (e.g., the photowidget 812 of FIG. 8) to permit a user to upload a picture to the newmark-up language file 214.

The reviews module 324 may be used to generate a reviews widget to allowa user to review media (e.g., review a song, artist, album, etc.) on theartist mark-up language file, the album mark up language file, theparticular item mark-up language file, the fan club mark-up languagefile and the new mark-up language file 214. The personal detail module326 may be used to generate a personal detail widget (e.g., the personaldetail widget 816 of FIG. 8) to allow a user to share personalinformation (e.g., Name, Age, Sex, etc.) on the new mark-up languagefile 214. The internal messaging module 328 may be used to generate aninternal messaging widget (e.g., the internal messaging widget 904 ofFIG. 9) to permit a user to communicate to other users on the serverdevice 100 (e.g., the server device 100 of FIG. 1) through the newmark-up language file 214. The share module 332 may be used to generatea share widget (e.g., the share widget 814 of FIG. 8) to allow a user toshare his/her mark-up language file with other users on the serverdevice 100. The media sample module 334 may be used to generate a mediasample widget to permit a user to sample a media segment (e.g., a 30second media segment) of certain items (e.g., a song, a movie, etc.) ofthe media data 116 that is associated with the play list history on thenew mark-up language file 214. In one embodiment, the play-list historydata may executable by interested parties (e.g., other users) as a radiostation (e.g., and/or a video station, a multi-media channel, as astreaming video channel, etc.).

The post module 330 may be used to generate a post widget (e.g., thepost widget 902 of FIG. 9) to allow a user to author (e.g., write) apost and the content of the post may be automatically displayed on thenew mark-up language file 214 as well as on an artist mark-up languagefile, an album mark-up language file, a particular item mark-up languagefile and/or a fan club mark-up language file, according to oneembodiment. In one embodiment the post module 330 may display thecontent data of the post before other content data (e.g., other contentdata of other posts) when a peer client device (e.g., the peer clientdevice 106 of FIG. 1) affiliated with the client device (e.g., theclient device 104 of FIG. 1) reaches the artist mark-up language file,the album mark-up language file, the particular item mark-up languagefile and/or the fan club mark-up language through the new mark-uplanguage file 214. For example, when a user say John Doe reaches anartist mark-up language file (e.g., the artist mark-up language file 900of FIG. 9 pertaining to Bob Dylan) through the new mark-up language file(e.g., the new mark-up language file 214 of FIG. 8 belonging to Evan deBoer), John Doe will see posts authored by Evan de Boer before otherposts on the Bob Dylan page.

In one embodiment the data analyzer 302 may analyze the media data 116and transmit it to populate the new mark-up language file 214 as perinstructions communicated by the media update module 304, the mediahistory module 306, the media rating module 308 and/or the widget selectmodule 310. The data analyzer 302 may analyze and/or organize the mediadata 116 by linking the meta-data identifier determined by the mediaprocessing module 202 (illustrated in FIG. 2) with its correspondingplay-list history data whose content has been identified by themeta-data identifier. The data analyzer 302 may also generate a userprofile by associating an arrangement of the play-list history data andthe new mark-up language file (e.g., the new mark-up language file 214of FIG. 2) which may include the arrangement of the play-list historydata to a user. The data analyzer 302 may communicate the user profileto the user profile database 206 (illustrated in FIG. 2).

The media update module 304 may be used to generate a media update(e.g., the media update 804 in FIG. 8) that may be displayed on the newmark-up language file 214 to reflect any changes to the user's mediacollection (e.g., recent movies added to collection, new books read,etc.). The media history module 306 may by used to provide a mediahistory (e.g., the media history 802 of FIG. 8) on the new mark-uplanguage file 214 to provide a chronology of the user's mediaconsumption (e.g., last songs played, last movies seen, etc.). The mediarating module 308 may be used to generate a media rating (e.g., themedia rating 806 of FIG. 8) on the new mark-up language file 214 basedon a statistical analysis of the user's media consumption (e.g., topsongs this month, top parties this month, etc.).

FIG. 4 is an exploded view of the client application module 110 of theclient device 104 of FIG. 1 having a data analyzer 400, a client devicescan module 402, a peripheral device scan module 404, a meta-dataidentifier module 406 and a play-list history module 408 according toone embodiment.

In one embodiment the client device 104 may communicate a media data(e.g., the media data 116 of FIG. 1) to a server device 100 to determineat least one meta-data identifier associated with the media data and/ormay automatically refresh a new mark-up language file (e.g., the newmark-up language file 214 of FIG. 2) using a play-list history dataassociated with certain items of the media data 116. The new mark-uplanguage file 214 may include a streamable version of the media data 116based on the meta-data identifier being referenced with a contentdatabase of the central server 118. The media data 116 may not betransferred from the client device 104 to the central server 118. Thestreamable version of the media data 116 may be accessable acrossdifferent client devices associated with the user. The client device 104may develop an arrangement of the existing media-collection dataassociated with the certain items of the media data 116. In particularthe client application module 110 may scan a client device 104(illustrated in FIG. 1) and/or a peripheral device 112 (illustrated inFIG. 1) for media data 116 (illustrated in FIG. 1), generate a play-listhistory of the media data 116, tag the media data with a meta-dataidentifier and/or communicate the media data 116 to a server device 100(illustrated in FIG. 1). The client device scan module 402 may scan formedia data (e.g., the media data 116 of FIG. 1) on the client device 104which may be a two-way mobile communication device (e.g., cell phone ofFIG. 5). The peripheral device scan module 404 may scan for media data(e.g., the media data 116 of FIG. 1) on the peripheral device 112(illustrated in FIG. 1) which may be a portable media player (e.g., mp3player of FIG. 5).

The meta-data identifier module 406 may be used to generate a meta-dataidentifier in a manner in which the client application module 110 may beagnostic of the type of media player application (e.g., unknown of thetype of media player application) compatible with the media data 116,according to one embodiment. The meta-data identifier module 406 maythen apply the meta-data identifier to tag the media data (e.g., themedia data 116 of FIG. 1 obtained by scanning the client device 104and/or the peripheral device 112) with a unique identifier in a mannerin which the client device 104 may be agnostic of the type of mediaplayer application compatible with the media data.

The play-list history module 408 may generate a play-list history fromthe media data 116 obtained from the client device 104 and/or theperipheral device 112 based on an analysis of the usage pattern of theclient device 104 and/or the peripheral device 112. The play-listhistory module 408 may also develop an arrangement of the play-listhistory data associated with the certain items of the media data 116,according to one embodiment. The data analyzer 400 may be used toanalyze the media data request from the server device 100 and mayprocess and compile the media data 116 (illustrated in FIG. 1) with thehelp of a processor (e.g., the processor 1012 of FIG. 10) by using theclient device scan module 402, the peripheral device scan module 404,the meta-data identifier module 406 and/or the play-list history module408 and communicate the media data 116 to the server device 100.

In one embodiment, operations may begin in the client device 104 of FIG.1 when it receives a request for media data from the media requestormodule 200 of FIG. 2. Specifically the media data request may bereceived by the data analyzer 400 of the client application module 110of FIG. 4. The client device scan module 402 may then scan the clientdevice for media data. Similarly the peripheral device scan module 404may also scan the peripheral device for media data. The media data maythen be received by the data analyzer 400 which may then link it to aunique meta-data identifier generated by the meta-data identifier module406. The play-list history module 408 may develop an arrangement of theplay-list history data based on analysis of the usage pattern of theclient device 104 and/or the peripheral device 112. The data analyzer400 may analyze the play-list history data and/or the meta-dataidentifier associated to the media data, compile the media data andcommunicate the media data to the server device 100 of FIG. 1.

FIG. 5 is a system view of the client application module 110 which mayextract and/or compile the media data 116 from a client device (e.g., acell phone) and/or a peripheral device (e.g., an mp3 player) andcommunicate the media data 116 over a network 102 to a server device100. The streaming module 500 may communicate streamable media content(e.g., audio, video, multimedia, etc.) from the central server 118through the server device 100 to the client group 114 accessed by theuser without requiring the consideration of the user. The server device100 may then process the media data 116 and/or automatically populatethe same on to a new mark-up language file 214.

FIG. 6 shows a diagrammatic representation of machine in the exampleform of a computer system 600 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In various embodiments, the machineoperates as a standalone device and/or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server and/or a client machine inserver-client network environment, and/or as a peer machine in apeer-to-peer (or distributed) network environment. The machine may be apersonal computer (PC), a tablet PC, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, anetwork router, switch and/or bridge, an embedded system and/or anymachine capable of executing a set of instructions (sequential and/orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individuallyand/or jointly execute a set (or multiple sets) of instructions toperform any one and/or more of the methodologies discussed herein.

The example computer system 600 includes a processor 602 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) and/orboth), a main memory 604 and a static memory 606, which communicate witheach other via a bus 608. The computer system 600 may further include avideo display unit 610 (e.g., a liquid crystal display (LCD) and/or acathode ray tube (CRT)). The computer system 600 also includes analphanumeric input device 612 (e.g., a keyboard), a cursor controldevice 614 (e.g., a mouse), a disk drive unit 616, a signal generationdevice 618 (e.g., a speaker) and a network interface device 620.

The disk drive unit 616 includes a machine-readable medium 622 on whichis stored one or more sets of instructions (e.g., software 624)embodying any one or more of the methodologies and/or functionsdescribed herein. The software 624 may also reside, completely and/or atleast partially, within the main memory 604 and/or within the processor602 during execution thereof by the computer system 600, the main memory604 and the processor 602 also constituting machine-readable media.

The software 624 may further be transmitted and/or received over anetwork 626 via the network interface device 620. While themachine-readable medium 622 is shown in an example embodiment to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium and/or multiple media (e.g., a centralizedand/or distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding and/or carrying a set of instructions for execution bythe machine and that cause the machine to perform any one or more of themethodologies of the various embodiments. The term “machine-readablemedium” shall accordingly be taken to include, but not be limited to,solid-state memories, optical and magnetic media, and carrier wavesignals.

FIG. 7 is a graphical user interface view of the widget select module310 used to select widgets for the new mark-up language file 214.Available widget view 700 shows a list of widgets that a user can pick.Chosen widget view 702 shows a list of widgets chosen from the availablewidget view 700. Widgets may be dragged and dropped from the availablewidget view 700 to the chosen widget view 702. Users can edit aparticular widget using the edit buttons in the chosen widget view 702.

FIG. 8 is a graphical interface view of a new mark-up language file 214of FIG. 2. Media collection 800 may show the entire media collection ofa user. Media history 802 may show a list of media consumed by a user ina chronological order (e.g., last songs played by a user). Media update804 may reflect any changes in a user's media collection (e.g., newmedia added to the user's collection). Media rating 806 may provide arating based on a statistical analysis of a user's media consumption(e.g., top artist, top song, etc.). Client group display 808 may showlist of other users connected to the user based on similarities in mediaconsumption of the user and the other users. Advertisement 810 may be anadvertisement from an interested party from whom a payment may beprocessed to display the advertisement on the new mark-up language file214. Photo widget 812 may be one of the widgets that a user can selectfrom the widget select module 310 to display a picture on the newmark-up language file 214. Share widget 814 may be a widget for a userto share his/her mark-up language file with other users on the serverdevice 100. Personal detail widget 816 may be a widget for a user toprovide his/her personal information (e.g., Name, Age, Sex, etc.) on thenew mark-up language file 214.

FIG. 9 is a graphical interface view of an artist mark-up language file900. Internal messaging widget 904 may be used to communicate with otherusers of the server device 100. Tag widget 906 may display a list oftags for a particular media and allow a user to provide a tag of his/herchoice for the particular media. Tuned-in now widget 908 may display alist of users tuned-in to a particular media in real time (e.g., list ofusers on the server device 100 listening to a particular song in realtime). Post widget 902 may allow a user to create a post on the newmark-up language file 214, the artist mark-up language file, the albummark-up language file, the particular item mark-up language file, and/orthe fan club mark-up language file.

FIG. 10 is a graphical interface view of the override module 212 of FIG.2. The interface may allow a user to modify contents associated to theplay-list history data (e.g., thereby generate a modified arrangement ofthe play-list history data) of the media data 116. Media history view1000 may provide a chronology of media consumed (e.g., last songsplayed). Media collection view 1002 may display the entire mediacollection held by a user. Client group view 1004 may display the groupformed by the relationship module 210 of FIG. 2 based on similarities inmedia consumption. Media update view 1006 may display the changes in auser's media collection (e.g., recently added to music collection). Usermay modify (e.g., add, delete, change and/or replace) contents with thehelp of adjust buttons provided in the user interface.

FIG. 11 is a flow chart illustrating a method to automatically populatea new mark-up language file (e.g., the new mark-up language file 214 ofFIG. 2) using an existing media collection data (e.g., a play-listhistory data) associated with certain items of the media data, accordingto one embodiment. In operation 1102, media data of a client device(e.g., client device 104 of FIG. 1) may be analyzed (e.g., by using dataanalyzer 218 of FIG. 2) to determine at least one meta-data identifierassociated with the media data. In operation 1104, a new mark-uplanguage file may be automatically populated using a existingmedia-collection data associated with certain items of the media data.In operation 1106, a streamable media content of the existingmedia-collection data may be created on the server device 100 based on areference of the at least one meta-data identifier associated with eachof the existing media collection data with a content database of acentral server (e.g., the central server 118 of FIG. 1). In operation1108, the streamable media content from the central server 118 may becommunicated to the user on any client device without requiringconsideration of the user to access the media content. The contentdatabase may include content of artists and media labels.

In operation 1110, the new mark-up language file 214 and the arrangementmay be associated with a particular user. In operation 1112, theparticular user may be associated with other mark-up language filesassociated with other users based on similar attributes in thearrangement of the particular user and other arrangements (e.g.,hierarchies) associated with the other users. In operation 1114, acompatibility rating may be determined (e.g., by using the relationshipmodule 210 of FIG. 2) between the user and the other users based on thesimilar attributes between the arrangement and the other arrangements.

FIG. 12 is a flow chart that describes further the operations in FIG.11, according to one embodiment. FIG. 12 begins with a ‘circle A’ thatconnotes a continuation from operation 1112 of FIG. 11 (e.g., FIG. 11concludes with the ‘circle A’). First in operation 1202, each user ofthe server device may be enabled to view mark-up language files of theother users. In operation 1204, a particular one of the other users maybe registered when the particular one of the other users responds to ahook data in a communication between the user and the other users. Inoperation 1206, a group (e.g., the client group 114 of FIG. 1) may beformed (e.g., by using the relationship module 210 of FIG. 2) betweenthe user and at least one of the other users based on a thresholdparameter of the compatibility rating. In operation 1208, a widgetchosen may be applied from a group (e.g., by using the widget selectmodule 310 of FIG. 3) comprising of a party widget, a tag widget, aguestbook widget, an internal messaging widget, a tuned-in now widget, apost widget, a reviews widget, and/or a live event widget to the newmark-up language file. In operation 1210, a payment may be processed(e.g., by using the transaction module 216 of FIG. 2) from an interestedparty when the new mark-up language file develops a patron base above athreshold value. In operation 1212, an advertisement of the interestedparty may be displayed on the new mark-up language file. In operation1214, the new mark-up language file may be localized in languagesincluding English, Japanese, Korean, Hindi, German, French, Russian,Arabic, Hebrew, Spanish, mandarin, Cantonese, and/or Italian.

FIG. 13 is a flow chart illustrating a method of the client device tocommunicate media data to the server device and refreshing a new mark-uplanguage file according to one embodiment. In operation 1302, a mediadata (e.g., the media data 116 of FIG. 1) may be communicated to aserver device to determine at least one meta-data identifier associatedwith the media data. In operation 1304, a new mark-up language file 214may be automatically refreshed using a existing media-collection dataassociated with certain items of the media data 116. The new mark-uplanguage file 214 may include a streamable version of the media data 116based on the meta-data identifier being referenced with a contentdatabase of a central server (e.g., the central server 118 of FIG. 1).In operation 1306, the meta-data identifier may be applied (e.g., by theclient application module 110 of FIG. 1) such that it is agnostic of atype of media player application compatible with the media data. Inoperation 1306, an arrangement of the existing media-collection dataassociated with the certain items of the media data may be developed.

Although the present embodiments have been described with reference tospecific example embodiments, it will be evident that variousmodifications and changes may be made to these embodiments withoutdeparting from the broader spirit and scope of the various embodiments.For example, the various devices, modules, analyzers, generators, etc.described herein may be enabled and operated using hardware circuitry(e.g., CMOS based logic circuitry), firmware, software and/or anycombination of hardware, firmware, and/or software (e.g., embodied in amachine readable medium).

For example, the client application module 110 (and all the modules inthe client application module 110 as illustrated in FIG. 4), the mediarequestor module 200, the media processing module 202, the profilegenerator module 204, the relationship module 210, the override module212, the transaction module 216, the widget generator module 300 (andall the modules within the widget generator module 300), the mediaupdate module 304, the media history module 306, the media rating module308, and/or the streaming module 500 may be enabled using transistors,logic gates, and electrical circuits (e.g., application specificintegrated ASIC circuitry) using a client circuit, a media requestercircuit, a media processing circuit, a profile generator circuit, arelationship circuit, a override circuit, a transaction circuit, awidget generator circuit, a media update circuit, a media historycircuit, a media rating circuit, a streaming circuit and/or circuits.

In addition, it will be appreciated that the various operations,processes, and methods disclosed herein may be embodied in amachine-readable medium and/or a machine accessible medium compatiblewith a data processing system (e.g., a computer system), and may beperformed in any order. Accordingly, the specification and drawings areto be regarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A method, comprising: analyzing, by a processorof a server device communicatively coupled to a client device through anetwork, a media data of the client device to determine at least onemeta-data identifier associated with the media data, wherein the atleast one meta-data identifier is generated by a client application ofthe client device that is agnostic of a type of media player applicationcompatible with the media data, wherein the media data is a multimediadata, and wherein the at least one meta-data identifier is determinedbased on an audio data embedded in the multimedia data; automaticallypopulating, by the processor of the service device, a new mark-uplanguage file using an existing media-collection data stored on theserver device and associated with the media data, wherein the newmark-up language file includes an arrangement of the existingmedia-collection data associated with the media data, wherein the newmark-up language file includes a 30 second media segment of the mediadata, and wherein the existing media-collection data is generated by aprocessor of the client device analyzing a usage pattern of the clientdevice; associating, by the processor of the service device, the newmark-up language file and the arrangement of the existingmedia-collection data with a user of the client device; processing, bythe processor of the server device, a payment from an interested partywhen the new mark-up language file develops a patron base above athreshold value; displaying, by the processor of the server device, anadvertisement of the interested party on the new mark-up language file;localizing, by the processor of the server device, the new mark-uplanguage file in at least one of a plurality of languages; registering,by the processor of the server device, a different user when thedifferent user responds to a hook data in a communication between theuser and the different user, wherein the hook data is at least one of anelectronic invitation to connect to the user or an electronic invitationto join a group comprising the user; identifying, by the processor ofthe server device, a different media data and a differentmedia-collection data of a different client device of the different usercommunicatively coupled with the server device; associating, by theprocessor of the sever device, the user with the different user based ona similar attribute in the arrangement of the existing media-collectiondata of the user and a different arrangement of the differentmedia-collection data of the different user; associating, by theprocessor of the server device, the different media-collection data ofthe different user with a different profile of the different user;automatically populating, by the processor of the server device, adifferent new mark-up language file of the different user when thedifferent media-collection data is identified by a different applicationmodule of the different client device; determining, by the processor ofthe server device, a compatibility rating between the user and thedifferent user based on the similar attribute between the arrangement ofthe existing media-collection data of the user and the differentarrangement of the different user; enabling, by the processor of theserver device, the user to view the different new mark-up language filebased on the determination of the compatibility rating; forming, by theprocessor of the server device, a group between the user and thedifferent user based on a threshold parameter of the compatibilityrating; applying, by the processor of the server device, a widget chosenfrom a widget group comprising of a party widget, a personal detailwidget, a tag widget, a guestbook widget, an internal messaging widget,a share widget, a photo widget, a tuned-in now widget, a post widget, areviews widget, and a live event widget to the new mark-up language fileand the different new mark-up language file; creating, by the processorof the server device, a stream of audio content based on the at leastone meta-data identifier, the new mark-up language file, the existingmedia-collection data, the different new mark-up language file, andcontent from a content database of a central server communicativelycoupled to the server device; and streaming, by the processor of theserver device, the stream of the audio content to the group.
 2. Themethod of claim 1, wherein the client device is a two-way mobilecommunication device.
 3. The method of claim 1, wherein the widget is adrag and drop widget, and wherein a content data created using the postwidget is automatically displayed on the new mark-up language file andat least one of an artist mark-up language file, an album mark-uplanguage file, a particular item mark-up language file, and a fan clubmark-up language file.
 4. A server device, configured to: analyze, by aprocessor of the server device communicatively coupled to a clientdevice through a network, a media data of the client device to determineat least one meta-data identifier associated with the media data,wherein the at least one meta-data identifier is generated by a clientapplication of the client device that is agnostic of a type of mediaplayer application compatible with the media data, wherein the mediadata is a multimedia data, and wherein the at least one meta-dataidentifier is determined based on an audio data embedded in themultimedia data; automatically populate, by the processor of the servicedevice, a new mark-up language file using an existing media-collectiondata stored on the server device and associated with the media data,wherein the new mark-up language file includes an arrangement of theexisting media-collection data associated with the media data, whereinthe new mark-up language file includes a 30 second media segment of themedia data, and wherein the existing media-collection data is generatedby a processor of the client device analyzing a usage pattern of theclient device; associate, by the processor of the service device, thenew mark-up language file and the arrangement of the existingmedia-collection data with a user of the client device; process, by theprocessor of the server device, a payment from an interested party whenthe new mark-up language file develops a patron base above a thresholdvalue; display, by the processor of the server device, an advertisementof the interested party on the new mark-up language file; localize, bythe processor of the server device, the new mark-up language file in atleast one of a plurality of languages; register, by the processor of theserver device, a different user when the different user responds to ahook data in a communication between the user and the different user,wherein the hook data is at least one of an electronic invitation toconnect to the user or an electronic invitation to join a groupcomprising the user; identify, by the processor of the server device, adifferent media data and a different media-collection data of adifferent client device of the different user communicatively coupledwith the server device; associate, by the processor of the sever device,the user with the different user based on a similar attribute in thearrangement of the existing media-collection data of the user and adifferent arrangement of the different media-collection data of thedifferent user; associate, by the processor of the server device, thedifferent media-collection data of the different user with a differentprofile of the different user; automatically populate, by the processorof the server device, a different new mark-up language file of thedifferent user when the different media-collection data is identified bya different application module of the different client device;determine, by the processor of the server device, a compatibility ratingbetween the user and the different user based on the similar attributebetween the arrangement of the existing media-collection data of theuser and the different arrangement of the different user; enable, by theprocessor of the server device, the user to view the different newmark-up language file based on the determination of the compatibilityrating; form, by the processor of the server device, a group between theuser and the different user based on a threshold parameter of thecompatibility rating; apply, by the processor of the server device, awidget chosen from a widget group comprising of a party widget, apersonal detail widget, a tag widget, a guestbook widget, an internalmessaging widget, a share widget, a photo widget, a tuned-in now widget,a post widget, a reviews widget, and a live event widget to the newmark-up language file and the different new mark-up language file;create, by the processor of the server device, a stream of audio contentbased on the at least one meta-data identifier, the new mark-up languagefile, the existing media-collection data, the different new mark-uplanguage file, and content from a content database of a central servercommunicatively coupled to the server device; and stream, by theprocessor of the server device, the stream of the audio content to thegroup.